Establishing and Maintenance of a Neighbour Relationship Between Access Nodes in a Wireless Communications Network

ABSTRACT

A method of establishing a relationship between access nodes in a wireless communications network is provided. An access node is registered with the network. Information about each access node registered with the network is then stored at a control node. A list is then compiled at the control node, which includes each access node registered with the network and the list indicates which access node is a neighbour of another access node. This neighbour list is sent from the control node to each access node in the network. When an access node detects other access nodes, this is reported to the control node, which updates the neighbour list to the access nodes.

FIELD OF THE INVENTION

The invention generally relates to a method of establishing a relationship between access nodes in a wireless communications network. More particularly, the invention relates to establishing and maintaining neighbour relations in a wireless communications network.

BACKGROUND OF THE INVENTION

Within 3GPP, in UTRAN or LTE macro wireless networks (radio access networks or RANs), a femtocell or Home Node B (HNB in a 3G network or H(e)NB in an LTE network) may perform the function of a Node B as an access node to the network but is optimized for use in a home or office (enterprise). Individual access points (HNBs or H(e)NBs are installed individually by end users, without strict supervision of the Mobile Network Operator (MNO).

In any wireless communications network, maintaining an up-to-date neighbor cell relationship is a difficult task for network operators, which requires detailed planning and exact implementation according to the plan. If there is any ambiguity or outdated information about neighbour cell relationships, a problem arises in that the erroneous information may be used in the access nodes of the network.

This in turn can lead to inaccurate information being provided to mobile terminals subscribed to the network, for example causing handover from one access node to another to fail. The neighbour cell relationship between access nodes needs to be provisioned at start-up to each access node and kept up to date so as to reflect the actual situation in the network. However, even when the network has been planned in detail and implemented exactly, errors during installation may still occur. The configuration, planning and installation effort of a wireless network should be reduced to a minimum in order to save time and money.

In the cases where a Home Node B network is involved, maintenance of an up-to-date neighbour cell relationship is further complicated by the fact that for a HNB, the node can be switched off and on by the user and therefore availability of related cell is not guaranteed. The basic principle behind uncoordinated deployment of H(e)NBs is that the H(e)NBs, while being part of the MNO's network are installed at the customers' premises in such a way that their deployment does not involve any kind of detailed network planning. Therefore the exact network topology is not known to the operator. This makes it difficult for the operator to become aware of neighbour relationships between the individual access nodes and in turn causes problems in creating cell reselection and handover procedures.

Since the network does not know the exact whereabouts of the H(e)NB, it cannot set up the neighbour list for each of the H(e)NBs; i.e., the list of potential targets for cell reselection (in idle mode) and for handover (in dedicated mode). The knowledge of the actual neighbour nodes of each individual H(e)NB is however necessary, as the mobile subscriber stations or user equipments (UEs) which are camping on a particular cell (in the case of 3G networks) have to be explicitly provided with a list of neighbouring access nodes whose signals these UEs have to measure and take into account in cell reselection procedures. This is also the case in the connected mode, where the UEs are provided with the list of neighbours to measure and report.

In coordinated deployments of macro networks, neighbour relationships between access nodes ((e)Node Bs) are determined using network planning and field measurements, since the MNO is fully aware of the physical location of each access node and can determine the exact neighbours of each access node. This information is then used to create a neighbour list (for 3G networks) or a neighbour relation table (For LTE ANR usage) for each access node in the network. Whenever a new node is added, the MNO can assess its impact on the existing network and possibly update the neighbour lists in the affected nodes.

In uncoordinated deployments, existing solutions for establishing neighbour relationships between H(e)NBs are based on the MNO estimating the neighbours of any given access node, which has a very limited degree of accuracy. Each of the users of the mobile network are supposed to provide their home addresses to the MNO when they subscribe to the network and each HNB is expected to provide information about the strongest detected macro node of the macro network it belongs to (in HNBAP HNB REGISTER REQUEST, as defined in 3GPP TS 25.469). These data can be used by the MNO to derive a tentative neighbour list for that node. As the configuration of H(e)NB parameters is performed automatically at the start-up phase, each H(e)NB receives a generic set of parameters from an Auto Configuration Server (ACS) so in theory there will be a general neighbour list valid for a certain area and all H(e)NBs supposedly located in this area will share the same list. However, updating this list is problematic, as the H(e)NB may be required to reboot or at least actively contact the ACS to obtain a new set of parameters including the NCL.

Another possible solution to populating the neighbour list in UTRAN and LTE networks is to enable Detected Set Reporting (DSR) by the UEs, where the UEs will report unsolicited neighbours that fulfill the reporting criteria. The downside of this is that it takes a long time to detect all possible neighbours. This means that at the initial stage, when the neighbour list is not complete, there could be a large number of handover failures.

The general problem of establishing and maintaining neighbour lists between H(e)NBs is illustrated in FIG. 1, which shows 10 H(e)NBs (H(e)NB 1 . . . 10) installed in 10 rooms (rooms 1 . . . 10), respectively on one floor of an office (enterprise) and able to access two macro networks Macro “A” and Macro “B”.

In order to enable the MNO to correctly configure the neighbour lists, the subscriber (in this case the enterprise) not only needs to inform the MNO about which H(e)NB is placed in which room but also about which rooms are the neighbouring rooms, as well as the H(e)NB identities and the position in the room where each H(e)NB is located. Even if there are GPS coordinates available for each of the H(e)NBs 1 . . . 10, the problem remains that the H(e)NBs may not be placed at the locations where they should have been according to planning, for example if two devices become confused with each other. FIG. 2 shows an exemplary neighbour list for three of the H(e)NBs H(e)NB 1, H(e)NB 2 and H(e)NB 10 located in rooms 1, 2 and 10, respectively. Including these H(e)NBs in the neighbour list as distributed by the management system of the network is certainly possible but requires a large effort and very detailed planning. However, these lists can only ever be an estimate and there is no guarantee that they reflect the reality of the situation. For example, if the subscriber had given the MNO wrong information about room location and room 6 was not in fact located opposite to room 1 across the corridor from it but rather on the same side of the corridor next to room 5, the information in the neighbour list of H(e)NBs would be completely wrong.

There is no existing method for a neighbour list of access nodes in a Femto or H(e)NB network to be established and maintained so that the list contains up-to-date information as to which access nodes are neighbours to each other.

It is thus an object of the present invention to overcome the above-mentioned drawbacks and allow neighbour relations to be established and maintained between H(e)NBs so that they are up-to-date, thereby facilitating successful handovers and avoiding failed handover situations.

SUMMARY OF THE INVENTION

Accordingly, in a first aspect, the invention provides a method of establishing a relationship between access nodes in a wireless communications network. The method includes registering an access node with the network, storing at a control node information about each access node registered with the network and compiling a list at the control node including each access node. The list indicates which said access node is a neighbour of another said access node; and sending the neighbour list from the control node to each said access node in the network.

Access nodes via which subscriber stations can access the wireless communications network register with the network and information about the registered access nodes is stored at a control node, for example in a database provided in the control node. Using the information obtained about each access node that registers with the network, the control node can then make a list of all the registered access nodes and indicate on the list which access nodes are neighbours with each other so that the list is a neighbour list or neighbourship relations list.

In this way, actual neighbour cell information is automatically provided to access nodes in the network, instead of merely an estimation, which avoids failed handovers. The initial configuration of a Neighbouring Cell List can be automated. In this way, H(e)NB networks can be configured more easily. Furthermore, the method according to the invention means that the effort involved in network planning for neighbour cells is reduced as the exact location of access points (H(e)NBs) is not required to be known.

The method may also include detecting at the access node other access nodes in the network. The access node can then also report information about itself, as well as about any other access nodes it has detected, to the control node.

In one embodiment, the access node receives the list from the control node. This neighbour list indicates which of the other access nodes detected by the access node its neighbouring access nodes. The neighbour list may then be updated to the access nodes in the network, either by the control node or by the access node itself. In this way, the automated initial configuration of Neighbouring Cell List and all possible updates to the Neighbour Cell List can be provided, which may happen after the start-up of an access node. This means that heterogeneous networks including H(e)NBs as part of a macro cell can be more easily maintained and kept up-to-date.

In a second aspect, the invention provides a method of establishing a relationship between access nodes in a wireless communications network. The method includes detecting at an access node other access nodes in the network, reporting information to a control node about the access node and the detected other access nodes, and receiving a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes.

The step of receiving may further includes receiving an update of the list of access nodes which are neighbouring access nodes.

In an advantageous embodiment, the method further includes sending a request to a subscriber station accessing the network to perform a measurement to detect available cells in the network. The measurement of detected available cells may then be received from the subscriber station and the access nodes of the detected available cells can be compared with the neighbour list received from the control node. Then the detected available cells that do not have access nodes contained in the neighbour list can be reported.

A request or order to the subscriber station to perform the measurement may be triggered if a cell parameter exceeds a predetermined threshold. The subscriber station can then measure n+1 . . . n+k available cells and, if it detects a potential neighbour cell from one of these cells, it can be reported to the control node that the detected cell is a new neighbour cell. This report may take place in a new information element provided in a message sent from the access node to the control node, for example in the HNBAP protocol.

In a third aspect, the invention provides a method of establishing a relationship between access nodes in a wireless communications network. The method includes receiving a command at a subscriber station to perform a measurement of a cell of the network, detecting available cells in the network at the subscriber station, performing the measurement of one of the available cells at the subscriber station. If the measurement is of a cell not contained in a neighbour cell list provided in the access node, then this measurement is reported to an access node of the network.

In a fourth aspect, the invention provides an access node for a wireless communications network. The access node includes a detector configured to detect other access nodes in the network. A transmitter is provided, which is configured to report information about the access node and the detected other access nodes to a control node controlling the access node. A receiver is configured to receive a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes. The receiver is further configured to receive an update of the list of access nodes which are neighbouring access nodes.

The access node may be a home Node B (HNB) as part of a UTRAN network or it may be a home eNode B (HeNB) as part of an LTE network.

Advantageously, the transmitter may be further configured to send a request to a subscriber station accessing the network to perform a measurement to detect available cells in the network. Then the receiver may be further configured to receive the measurement of detected available cells from the subscriber station. In this case, the access node may further include a comparator adapted to compare access nodes of the detected available cells with the neighbour list received from the control node. The access node can be further configured to report the detected available cells that do not have access nodes contained in the neighbour list.

The access node can be triggered to send the request or order to the subscriber station to perform the measurement of n+1 . . . n+k cells in order to find potential neighbour cells (e.g. Detected Set Reporting) if a measurement of a cell parameter exceeds a predetermined threshold.

Once a new neighbour has been found out of the n+1 . . . n+k cells by the subscriber station and reported back to the access node, the access node may then report to the control node (e.g. HNB-GW or HMS) that the detected cell is a new neighbour cell, for example by using a new information element inserted in messages between the access node and the control node. This could simply be achieved by an extension to existing protocols, for example HNBAP.

In a fifth aspect, the invention provides a control node for a wireless communications network, which includes a receiver configured to receive information about access nodes registered with the network and a database configured to store said information about the access nodes. A processor is also provided, which is configured to derive neighbour relationships between the access nodes from said information and to create a neighbour list of the access nodes, as well as a transmitter, which is configured to send the neighbour list to the access nodes.

The control node may be a home (e)Node B gateway (HNB-GW) or a home (e)Node B management system (HMS), for example.

The transmitter of the control node may be further configured to update the neighbour list to the access nodes.

In a sixth aspect, the invention provides a subscriber station for accessing a wireless communications network. The subscriber station includes a receiver configured to receive a command to perform a measurement of a cell of the network and a detector configured to detect available cells. A measurement apparatus is configured to perform the measurement of one of the available cells and a transmitter is configured to report the measurement to an access node of the network when the measurement is of a cell not contained in a neighbour cell list provided in the access node.

In a seventh aspect, the invention provides a computer program product adapted to run on a processor in a control node of a wireless communications network. The computer program product is adapted to control the control node to perform the steps of registering an access node with the network, storing information in the control node about each said access node registered with the network, and compiling a list at the control node including each said access node, wherein list indicates which access node is a neighbour of another access node, and sending the neighbour list from the control node to each access node in the network.

In an eighth aspect, the invention provides a computer program product adapted to run on a processor in an access node of a communications network, wherein the computer program product is configured to control the access node to perform the steps of detecting at the access node other access nodes in the network, reporting information to a control node about the access node and the detected other access nodes, and receiving a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes.

In a ninth aspect, the invention provides a computer program product adapted to run on a processor in a subscriber station, wherein the computer program product is configured to control the subscriber station to perform the steps of receiving a command to perform a measurement of a cell of the network, detecting available cells in the network, performing a measurement of one of the available cells and reporting the measurement to an access node of the network when the measurement is of a cell not contained in a neighbour cell list provided in the access node.

The invention will now be described, by way of example only, with reference to specific embodiments, and to the accompanying drawings, in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified schematic block diagram of an arrangement of H(e)NBs used as access nodes for a wireless communications network in an office (enterprise situation);

FIG. 2 is an example of a neighbour list of the H(e)NBs shown in FIG. 1 distributed by a management system of the network;

FIG. 3 is a simplified schematic block diagram of a wireless communications network in which a method according to an embodiment of the invention may be implemented;

FIG. 4 is a simplified schematic block diagram of an access node according to an embodiment of the invention;

FIG. 5 is a simplified schematic block diagram of a control node according to an embodiment of the invention;

FIG. 6 is a simplified schematic block diagram of a subscriber station according to an embodiment of the invention;

FIG. 7 is an exemplary message flow diagram used in a method according to an embodiment of the invention;

FIG. 8 is a schematic block diagram of information provided to the network by each access node;

FIG. 9 is a schematic block diagram of a neighbour list derived by a method according to an embodiment of the invention;

FIG. 10 is an exemplary list of cells stored in an access node; and

FIG. 11 is an exemplary message flow diagram used in a method according to an embodiment of the invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

FIG. 3 shows a wireless communications network having femtocells as part of a macro network run by a mobile network operator (MNO). The femtocells may be part of an enterprise, for example, which subscribes to the macro network and each femtocell has an access point provided by a home node B (HNB) HNB1, HNB2, HNB3. In the following exemplary embodiments, three HNBs are shown although there may be more or fewer in such a network. A mobile subscriber station or user equipment (UE) UE1 may access the network via one of the HNBs HNB1, HNB2, HNB3.

Each of the HNBs are coupled over an interface to a home node B gateway (HNB-GW) 10, which is a control node for controlling the HNBs. The HNBs are also coupled to a Home Node B Management Server (HMS) (not shown). Together the HNB-GW and HMS take part in performing operation and maintenance (O&M) functions.

Each HNB HNB1, HNB2, HNB3 has a transmitter T1, a receiver R1, a detector 11 and a comparator C, as shown in FIG. 4. FIG. 5 schematically shows the HNB-GW 10, which has a transmitter T2, a receiver R2 a database D and a processor P; and FIG. 6 schematically shows the UE 1, which has a transmitter T3, a receiver R3, and a detector 12 for detecting and measuring available cells. The HNBs HNB1, HNB2, HNB3, the HNB-GW 10 and the UE1 are all further provided with processors for running software to perform the method according to embodiments of the invention.

During start-up of a HNB (e.g. HNB 1) the device already performs a radio scan, eventually limited by the management system to a limited number of predefined frequencies of frequency ranges. This is done primarily to ensure that HNB HNB 1 is not activating its transmitter T1 while not located in the location initially negotiated between the mobile network operator and the subscriber. For this purpose the management system pre-configures, for example some base stations belonging to the macro network that need to be detected and reported to the HNB-GW 10. However, in a dense HNB deployment situation as for example in an enterprise scenario, the detector 11 in the HNB HNB 1 will also detect nearby HNBs, for example HNB 2 and HNB 3, which may or may not be preconfigured by the management system of the mobile network operator.

The HNB-GW 10 creates and maintains the database D, which stores H(e)NB identities along with associated information to derive neighbour relations between HNBs HNB1, HNB2, HNB3 served by the HNB-GW 10. The HNB-GW 10 also distributes relevant parts of the list to the HNBs HNB1, HNB2, HNB3 while they are being registered with the network, as well as updating them whenever the neighbour relations change due to newly registered or deregistered HNBs. The HNB-GW 10 collects the data necessary to fill the database D from individual HNB HNBAP REGISTER REQUEST messages, for example. The initial list of relevant neighbours is then provided back to the HNB HNB1, HNB2, HNB3, which it receives at the receiver R1 in HNBAP REGISTER ACCEPT messages, for example. The update of the neighbour list can then be sent to the HNB HNB1, HNB2, HNB3 using a new dedicated HNBAP message, e.g. HNBAP NEIGHBOUR UPDATE message, as illustrated in the message flow diagram in FIG. 7. Additionally the HNB-GW 10 may check and resolve unidirectionality, for example HNB 1 receives the signal from HNB2 but not vice versa.

Each HNB HNB1, HNB2, HNB3 needs to register itself at the HNB-GW 10. During the registration process it provides the HNB-GW 10 with several parameters in a HNBAP REGISTER REQUEST message (see 3GPP TS 25.469) as shown in Table 1.

TABLE 1 HNBAP REGISTER REQUEST message Semantics Assigned PARAMETER PRESENCE RANGE Description Criticality Criticality Message Type M YES reject HNB Identity M YES reject HNB Location Information M YES reject PLMN-ID M YES reject Cell-ID M YES reject LAC M YES reject RAC M YES reject SAC M YES reject CSG-ID O YES reject Service Area For Broad- O YES ignore cast HNB Cell Access Mode O YES reject

The HNB Location Information IE is sent from the HNB to HNB-GW to provide information on the location of the HNB HNB1, HNB2, HNB 3 and an example of the information that could be provided is illustrated in Table 2.

TABLE 2 HNB Location Information IE IE/GROUP NAME PRESEN RANG Semantics Critical- Assigned HNB Location — — Infor- > Macro O — — Coverage Information > Geographic O — — Location > HNB Internet O YES reject Information

The data contained in the location information may either come from the HMS (e.g. geographic location), or be provided by the HNB HNB1, HNB2, HNB 3 itself (e.g. macro coverage, geographic location). These data can then be made available for the HNB-GW 10, so that it can derive potential geographical associations between the HNBs HNB1, HNB2, HNB3 that it controls.

Therefore as soon as a new HNB, e.g. HNB 1 registers itself with the network, its coordinates are added to the database D in the HNB-GW 10, a tentative list of neighbour cells is derived and the list is sent back to the HNB HNB 1 in the HNBAP REGISTER ACCEPT message. The content of the message is shown in Table 3, although it is not limited to that shown in Table 3 and may include additional and/or alternative elements.

TABLE 3 HNBAP REGISTER RESPONSE message Assigned PARAMETER PRESENCE RANGE Semantics Description Criticality Criticality Message Type M YES reject RNC-ID M YES reject Mux Port Number O The mux port number YES Ignore at which HNB-GW expects to receive multiplexed packets. Neighbour Information O 0 to YES reject List max- noof- Neighbours PLMN-ID M PLMN ID of HNB YES reject neighbour cell Cell-ID M Cell ID of HNB YES reject neighbour cell CSG-ID M CSG-ID of each configured YES reject neighbour cell

The list of neighbours contained in the HNBAP REGISTER RESPONSE message represents the state of the network at the moment of the registration of the given HNB. In order to allow for more dynamic behaviour, a new HNBAP message is required. The new message, HNBAP NEIGHBOUR UPDATE, is sent to the relevant HNBs each time the neighbourship relation is modified. The modification occurs when a) new HNB registers at the HNB-GW 10, b) any of the registered HNBs HNB1, HNB2, HNB3 deregister themselves from the HNB-GW 10. At each occurrence of such an event, the HNB-GW 10 reassesses the neighbour relationship table, to determine which HNBs need to be updated about the modification of their neighbours. The new HNBAP message can be an unacknowledged message sent from HNB-GW 10 to an HNB HNB1, HNB2, HNB3, and conveys the following data as shown in Table 4.

TABLE 4 HNBAP NEIGHBOUR UPDATE message Assigned PARAMETER PRESENCE RANGE Semantics Description Criticality Criticality Message Type M YES reject Update status M Enumerated: Indicates which action YES reject [add, HNB has to take remove, update] PLMN-ID M PLMN ID of HNB YES reject neighbour cell Cell-ID M Cell ID of HNB YES reject neighbour cell CSG-ID M CSG-ID of neighbour YES reject cell PSC M PSC value used by the YES reject neighbour cell

The neighbour list, and the neighbour update message, may also be enhanced with additional information about the neighbours. For example, if an HNB is enabled to establish a direct communication path to another HNB, the information required in support of such feature could also be provided, e.g. Transport Layer Address.

Exemplarily the three HNBs HNB1, HNB2 and HNB3 can be considered, along with the information each one reports to the HNB-GW 10 during registration in a registration request, which is illustrated in Figure . . . . It can be seen from FIG. 8 that every HNB HNB1, HNB2 and HNB3 provides a set of information to the network, including PLMN-ID, Cell-ID, LAC, RAC, SAC, CSG-ID and Access Mode. The arrows on the right hand side of FIG. 8 show the relations the HNB-GW 10 would derive based on this registration information. It should be noted that a HNB performs the radio scan at minimum during start-up, as performing the scan while in operation would require the transmitter T1 of the HNB to be switched off. Therefore, after having received these three registration requests from the HNB, the HNB-GW 10 is able to visualize the neighbour relations per HNB in the network in a neighbour list. An example of a neighbour list for the HNBs as derived by the HNB-GW 10 is set out as a table as shown in FIG. 9.

In an advantageous embodiment, which is applicable to the case where the wireless communications network is a UTRAN network, the HNB HNB1 requests the UE 1 attached to it, to perform a “Detected Set Reporting” (DSR) measurement for detecting available cells. The UE1 receives the request at the receiver R3, detects and measures available cells using the detector 12 and sends a measurement report to the HNB HNB1 from the transmitter T3. The HNB HNB1 receives a measurement report from the UE1 at the receiver R1 and the comparator C compares the result of the measurement with the currently known neighbouring cell list stored in the database D. In case the measurement report UE1 reveals a currently unknown neighbour not contained on the known list, the HNB 1 then reports the detected new neighbour cell to the HNB-GW 10 using an appropriate message sent from the transmitter T1, which can be newly defined. The HNB-GW 10 incorporates this newly reported neighbouring HNB onto the neighbour list and informs the concerned neighbouring HNBs HNB1, HNB2 and HNB3 accordingly by updating the neighbour list to them.

In a further development of the embodiment described above, the existing neighbour cell handling infrastructure (RRM software) within a HNB HNB1, HNB2, HNB3 is used to gain information as to which cells are located in the neighbourhood of the HNB HNB1, HNB2, HNB3.

It is assumed that each connected HNB HNB1, HNB2, HNB3 is able to exchange relevant information about its working status to the remote operation and maintenance centre (O&M), which includes the HMS and the HNB-GW 10. The details of the information exchange are specific to each Mobile Network Operator. Information which is provided by the O&M in the provisioning and configuration stage is described in 3GPP 25.467 v9.2.0 section 6.1 and includes a list of neighbouring cells relevant for mobility decisions (such as handovers and measurements) acquired during the initial Network Listening Mode (NLM) and consisting of overlaying macro-cells and other HNBs in the nearest vicinity. A list of Primary Scrambling Codes (PSCs) representing the cells is also included. This can be taken from the CSG PSC Split information, which this cell as a hybrid or closed cell is aware of, since it has to broadcast this information to the UE 1.

Therefore, each HNB HNB1, HNB2, HNB3 has the following list of cells as illustrated in FIG. 10:

Cells n+1 to n+k include a PSC coming from the PSC CSG split range but excluding any PSC that has been already discovered during the NLM. This is due to the fact that the initial radio environment scan guarantees no PSC confusion of cells in direct neighbourhood. This narrows down the number of potential neighbouring PSCs (for cells n+1 to n+k).

An exemplary message flow for this embodiment is shown in FIG. 11. If the UE 1 is in CELL DCH state, the HNB HNB1, HNB2, or HNB3 configures the UE 1 to report the measurement event 1E for cells n+1 to cell n+k. Measurement event 1E is an existing intra-frequency measurement, and specified in 3GPP TS 25.331. If the UE 1 is able to detect one or several available cells n+1 to n+k, and if the P-CPICH of one of these cells exceeds the absolute threshold as set in 1E, then the UE 1 is triggered to send a measurement report 1E to the HNB HNB1, HNB2, HNB3. The measurement report includes information about whether a detected available cell is a new neighbour cell.

The HNB HNB1, HNB2, HNB3 stores the information that this cell was detected and reports to the HNB-GW 10, by using an information element added to the HNBAP protocol, that the detected cell is a new neighbour cell. When multiple UEs perform measurement over a time period, information can be collected as to how frequently neighbouring cells were detected.

This provides a much faster way of measuring neighbouring cells and uses a limited number of scrambling codes.

Although the invention has been described hereinabove with reference to specific embodiments, it is not limited to these embodiments and no doubt further alternatives will occur to the skilled person, which lie within the scope of the invention as claimed.

For example, the invention has been described with reference to a UTRAN network. However, it could apply equally to an LTE network, in which case the HNB and HNB-GW 10 would be replace with H(e)NB and H(e)NB-GW, respectively.

For the purpose of the present invention as described herein above, it should be noted that:

-   -   an access technology via which signaling is transferred to and         from a network element or node may be any technology by means of         which a node can access an access network (e.g. via a base         station or (e)Node B or generally an access node). Any present         or future technology, such as GSM, UTRAN, LTE, WLAN (Wireless         Local Access Network), WiMAX (Worldwide Interoperability for         Microwave Access), BlueTooth, Infrared, and the like may be         used; although the above technologies are mostly wireless access         technologies, e.g. in different radio spectra, access technology         in the sense of the present invention implies also wirebound         technologies, e.g. IP based access technologies like cable         networks or fixed lines but also circuit switched access         technologies; access technologies may be distinguishable in at         least two categories or access domains such as packet switched         and circuit switched, but the existence of more than two access         domains does not impede the invention being applied thereto,     -   usable access networks may be any device, apparatus, unit or         means by which a station, entity or other user equipment may         connect to and/or utilize services offered by the access         network; such services include, among others, data and/or         (audio-) visual communication, data download etc.;     -   a user equipment may be any device, apparatus, unit or means by         which a system user or subscriber may experience services from         an access network, such as a mobile phone, personal digital         assistant PDA, or computer;     -   method steps likely to be implemented as software code portions         and being run using a processor at a network element or terminal         (as examples of devices, apparatuses and/or modules thereof, or         as examples of entities including apparatuses and/or modules         therefor), are software code independent and can be specified         using any known or future developed programming language as long         as the functionality defined by the method steps is preserved;     -   generally, any method step is suitable to be implemented as         software or by hardware without changing the idea of the         invention in terms of the functionality implemented;     -   method steps and/or devices, apparatuses, units or means likely         to be implemented as hardware components at a terminal or         network element, or any module(s) thereof, are hardware         independent and can be implemented using any known or future         developed hardware technology or any hybrids of these, such as         MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS         (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled         Logic), TTL (Transistor-Transistor Logic), etc., using for         example ASIC (Application Specific IC (Integrated Circuit))         components, FPGA (Field-programmable Gate Arrays) components,         CPLD (Complex Programmable Logic Device) components or DSP         (Digital Signal Processor) components; in addition, any method         steps and/or devices, units or means likely to be implemented as         software components may for example be based on any security         architecture capable e.g. of authentication, authorization,         keying and/or traffic protection;     -   devices, apparatuses, units or means can be implemented as         individual devices, apparatuses, units or means, but this does         not exclude that they are implemented in a distributed fashion         throughout the system, as long as the functionality of the         device, apparatus, unit or means is preserved,     -   an apparatus may be represented by a semiconductor chip, a         chipset, or a (hardware) module comprising such chip or chipset;         this, however, does not exclude the possibility that a         functionality of an apparatus or module, instead of being         hardware implemented, be implemented as software in a (software)         module such as a computer program or a computer program product         comprising executable software code portions for execution/being         run on a processor;     -   a device may be regarded as an apparatus or as an assembly of         more than one apparatus, whether functionally in cooperation         with each other or functionally independently of each other but         in a same device housing, for example.

LIST OF ABBREVIATIONS

-   -   ACS Auto Configuration Server     -   ANR Automatic Neighbourhood Relation     -   CN Core Network     -   CPICH Common Pilot Channel     -   DSR Detected Set Reporting     -   H(e)NB Home Evolved Node B     -   HMS Home Node B Management System     -   HNB Home Node B     -   HNBAP Home Node B Application Part     -   HNB-GW Home NodeB Gateway     -   HO Hand-over     -   IE Information Element     -   IP Internet Protocol     -   LTE Long Term Evolution     -   MNO Mobile Network Operator     -   NCL Neighbouring Cell List     -   PSC Primary Scrambling Code     -   O&M Operation and Maintenance     -   UE User Equipment     -   UTRAN Universal Terrestrial Radio Access Network     -   RRM Radio Resource Management     -   RNC Radio Network Controller     -   RSSI Received Signal Strength Indicator 

1. A method of establishing a relationship between access nodes in a wireless communications network, the method comprising: registering an access node with the network; storing at a control node information about each said access node registered with the network; compiling a list at the control node including each said access node, wherein the list indicates which said access node is a neighbour of another said access node; and sending the neighbour list from the control node to each said access node in the network.
 2. The method according to claim 1, further comprising detecting at the access node other access nodes in the network.
 3. The method according to claim 2, further comprising reporting information about the access node and the detected other access nodes to the control node.
 4. The method according to claim 3, further comprising receiving at the access node the list from the control node, wherein the list indicates which of the detected other access nodes are neighbouring access nodes to said access node.
 5. The method according to claim 1, further comprising updating the neighbour list to the access nodes.
 6. A method of establishing a relationship between access nodes in a wireless communications network, the method comprising: detecting at an access node other access nodes in the network; reporting information to a control node about the access node and the detected other access nodes; and receiving a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes.
 7. The method according to claim 6, wherein the step of receiving further comprises receiving an update of the list of access nodes which are neighbouring access nodes.
 8. The method according to claim 6, further comprising sending a request to a subscriber station accessing the network to perform a measurement to detect an available cell in the network.
 9. The method according to claim 8, further comprising receiving the measurement of the detected available cell from the subscriber station.
 10. The method according to claim 8, wherein the detected available cell is triggered to be reported by the subscriber station to the access node if the measurement includes a cell parameter exceeding a predetermined threshold.
 11. The method according to claim 9, further comprising comparing access nodes of the detected available cells with the neighbour list received from the control node.
 12. The method according to claim 11, further comprising reporting the detected available cell if it does not have an access node contained in the neighbour list.
 13. The method according to claim 10, further comprising informing the control node that the detected available cell is a new neighbour cell.
 14. A method of establishing a relationship between access nodes in a wireless communications network, the method comprising: receiving a command at a subscriber station to perform a measurement of a cell of the network; detecting available cells in the network at the subscriber station; performing said measurement of one of the available cells at the subscriber station; and reporting said measurement to an access node of the net-work when the measurement is of a cell not contained in a neighbour cell list provided in the access node.
 15. An access node for a wireless communications net-work, the access node comprising: a detector configured to detect other access nodes in the network; a transmitter configured to report information about the access node and the detected other access nodes to a control node controlling the access node; and a receiver configured to receive a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes.
 16. The access node according to claim 15, wherein the receiver is further configured to receive an update of the list of access nodes which are neighbouring access nodes.
 17. The access node according to claim 15, wherein the transmitter is further configured to send a request to a subscriber station accessing the network to perform a measurement to detect available cells in the network.
 18. The access node according to claim 17, wherein the transmitter is configured to send said request to the subscriber station when a cell parameter exceeds a predetermined threshold.
 19. The access node according to claim 17, wherein the receiver is further configured to receive the measurement of detected available cells from the subscriber station.
 20. The access node according to claim 19, wherein the transmitter is further configured to inform the control node that one of the detected available cells is a new neighbour cell.
 21. The access node according to claim 19, further comprising a comparator adapted to compare access nodes of the detected available cells with the neighbour list received from the control node.
 22. The access node according to claim 19, wherein the transmitter is further configured to report the detected available cells that do not have access nodes contained in the neighbour list.
 23. A control node for a wireless communications network, the control node comprising: a receiver configured to receive information about access nodes registered with the network; a database configured to store said information about the access nodes; a processor configured to derive neighbour relationships between the access nodes from said information and to create a neighbour list of the access nodes; and a transmitter configured to send the neighbour list to the access nodes.
 24. The control node according to claim 19, wherein the transmitter is further configured to update the neighbour list to the access nodes.
 25. A subscriber station for accessing a wireless communications network, the subscriber station comprising: a receiver configured to receive a command to perform a measurement of a cell of the network; a detector configured to detect available cells; a measurement apparatus configured to perform said measurement on one of the available cells; and a transmitter configured to report said measurement to an access node of the network when the measurement is of a cell not contained in a neighbour cell list provided in the access node.
 26. A computer program product adapted to run on a processor in a control node of a wireless communications network, wherein the computer program product is adapted to control the control node to perform the steps of: registering an access node with the network; storing information in the control node about each said access node registered with the network; compiling a list at the control node including each said access node, wherein the list indicates which said access node is a neighbour of another said access node; and sending the neighbour list from the control node to each said access node in the network.
 27. A computer program product adapted to run on a processor in an access node of a communications network, wherein the computer program product is configured to control the access node to perform the steps of: detecting at the access node other access nodes in the network; reporting information to a control node about the access node and the detected other access nodes; and receiving a neighbour list from the control node containing a list of access nodes which are neighbouring access nodes.
 28. A computer program product adapted to run on a processor in a subscriber station, wherein the computer program product is configured to control the subscriber station to perform the steps of: receiving a command to perform a measurement of a cell of the network; detecting available cells in the network; performing said measurement of one of the available cells; and reporting said measurement to an access node of the network when the measurement is of a cell not contained in a neighbour cell list provided in the access node. 